You will optimize a provided website with a number of optimization- and performance-related issues so that it achieves a target PageSpeed score and runs at 60 frames per second.

Evaluation and Submission

Evaluation

Your project will be evaluated by a Udacity reviewer according to the Website Performance Optimization Rubric. Be sure to review it thoroughly before you submit. All criteria must "meet specifications" in order to pass.

Submission

Submit both your source and production code in the same repository in separate directories. These directories are usually named src and dist respectively.
If build tools are used the gulp or grunt.js file as well as the package.json file must be included in the submission.
If build tools are used, the instructions for building the project and running the tool must be included in the README.md. You may find the short Writing READMEs course helpful.
The node_modules directory may contain thousands of files and should not be contained in the submission. See the forum post how to remove node_modules directory from Github repository for instructions.
The master branch is the default Github repository branch. If you wish to submit another branch, you'll need to set it as the new default branch inside your Github repository.
When you're ready to submit your project go back to your Udacity Home, click on Project 5, and we'll walk you through the rest of the submission process. Due to the high volume of submissions we receive, please allow up up to 7 business days for your evaluation to be returned.
If you are having any problems submitting your project or wish to check on the status of your submission, please email us at frontend-project@udacity.com or visit us in the discussion forums.

What's Next?

You will get an email as soon as your reviewer has feedback for you. In the meantime, review your next project and feel free to get started on it or the courses supporting it!